Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1e6d5cb3b6396d5f00a5f4ca330a76116c208eb2eed99109ff364b53917dfc

Tx prefix hash: 804eed7a62956ef2fa3f00ef361262cfc53040f9316f7036e34829e012ce9ebe
Tx public key: 463bbdc5f16b9fa73855588862965f7d3c2fb937bf876835c0ca53b727e50d72
Timestamp: 1770900376 Timestamp [UTC]: 2026-02-12 12:46:16 Age [y:d:h:m:s]: 00:004:03:52:45
Block: 1476226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 2944 RingCT/type: yes/0
Extra: 01463bbdc5f16b9fa73855588862965f7d3c2fb937bf876835c0ca53b727e50d7202088e3d62bc3b0b07c3

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0d3782e6b88bb1b104723e77e9ea6143d15859e3b088fb51c7a8a1d38e2d538f 0.000600000000 1965530 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 dinastycoin-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": 1476236, "vin": [ { "gen": { "height": 1476226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d3782e6b88bb1b104723e77e9ea6143d15859e3b088fb51c7a8a1d38e2d538f" } } ], "extra": [ 1, 70, 59, 189, 197, 241, 107, 159, 167, 56, 85, 88, 136, 98, 150, 95, 125, 60, 47, 185, 55, 191, 135, 104, 53, 192, 202, 83, 183, 39, 229, 13, 114, 2, 8, 142, 61, 98, 188, 59, 11, 7, 195 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369