Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fc7f1453a0ad9b1673dcf6cd94c25236b439c3d2ae2d2295e53499fcab771bc

Tx prefix hash: 8cef40ad9eec231a293db782f21823e5609ba0089c4f361affe81ef6d525f314
Tx public key: 6a1ae8b842ffde2aede91187aedcf2c6d794c0a4acb10af44ab10f106e3faca4
Timestamp: 1764785739 Timestamp [UCT]: 2025-12-03 18:15:39 Age [y:d:h:m:s]: 00:036:14:13:04
Block: 1425732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26196 RingCT/type: yes/0
Extra: 016a1ae8b842ffde2aede91187aedcf2c6d794c0a4acb10af44ab10f106e3faca4021100000003fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c0e586da987c2017f90e86dd83a1da863604821906bfb2f7893cceea47ed6a2 0.600000000000 1914399 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": 1425742, "vin": [ { "gen": { "height": 1425732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c0e586da987c2017f90e86dd83a1da863604821906bfb2f7893cceea47ed6a2" } } ], "extra": [ 1, 106, 26, 232, 184, 66, 255, 222, 42, 237, 233, 17, 135, 174, 220, 242, 198, 215, 148, 192, 164, 172, 177, 10, 244, 74, 177, 15, 16, 110, 63, 172, 164, 2, 17, 0, 0, 0, 3, 251, 143, 208, 137, 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