Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 6e158016c6376df1c61977401a765fb670c8b918282fbfa5b0718cb6cd8bfb1e

Tx prefix hash: f9d0c78e792ec71efd0b676596e5a0227c8dfbeb4b1c24cac7326dad6ad9ef15
Tx public key: 9ec9909ee7206b2d26f802cef54216f13770b620e1c9c77cc259c79701a452f5
Timestamp: 1763508252 Timestamp [UCT]: 2025-11-18 23:24:12 Age [y:d:h:m:s]: 00:009:06:58:18
Block: 1415131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6655 RingCT/type: yes/0
Extra: 019ec9909ee7206b2d26f802cef54216f13770b620e1c9c77cc259c79701a452f50211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3ddb6e190f71a34b88109ab3128d8946dd4ebf3c0a28dd5d140b118f0ad7855 0.600000000000 1903626 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1415141, "vin": [ { "gen": { "height": 1415131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3ddb6e190f71a34b88109ab3128d8946dd4ebf3c0a28dd5d140b118f0ad7855" } } ], "extra": [ 1, 158, 201, 144, 158, 231, 32, 107, 45, 38, 248, 2, 206, 245, 66, 22, 241, 55, 112, 182, 32, 225, 201, 199, 124, 194, 89, 199, 151, 1, 164, 82, 245, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8