Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee0b783c7eff79dd0ced6bd1996866063cd26c72fd698c3c672a7172e29c8fc2

Tx prefix hash: 7cbbd4c0aadd84083414326448591d2e4c5f74dd59cdbf66536fdf0a211f1cc3
Tx public key: 2f520065d60ef3f899983a50b1938709f85ad894104e1f6fee3e35a0e7c019b8
Timestamp: 1759913827 Timestamp [UCT]: 2025-10-08 08:57:07 Age [y:d:h:m:s]: 00:087:03:06:41
Block: 1385333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62406 RingCT/type: yes/0
Extra: 012f520065d60ef3f899983a50b1938709f85ad894104e1f6fee3e35a0e7c019b8021100000004a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff9e02d065d8fa956a329095f2e052a2109f5bb992a04c829134fdbaa828a33c 0.600000000000 1873496 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": 1385343, "vin": [ { "gen": { "height": 1385333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff9e02d065d8fa956a329095f2e052a2109f5bb992a04c829134fdbaa828a33c" } } ], "extra": [ 1, 47, 82, 0, 101, 214, 14, 243, 248, 153, 152, 58, 80, 177, 147, 135, 9, 248, 90, 216, 148, 16, 78, 31, 111, 238, 62, 53, 160, 231, 192, 25, 184, 2, 17, 0, 0, 0, 4, 165, 220, 205, 121, 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