Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 898f825c09047848459f597b81239ccdf03b49cb5b04c2da0d51c3e7ccf3b50d

Tx prefix hash: 912f1990da56cd9d0d31af7d8b06b87dbf26fe9182ba0ef3bd4844b9eacd7e25
Tx public key: 635d3cfbdce55d361574ecc15bd6002d4a5ca11df774d77fb91bf310a4df620d
Timestamp: 1758930292 Timestamp [UCT]: 2025-09-26 23:44:52 Age [y:d:h:m:s]: 00:044:21:53:51
Block: 1377194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32157 RingCT/type: yes/0
Extra: 01635d3cfbdce55d361574ecc15bd6002d4a5ca11df774d77fb91bf310a4df620d02110000000597baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bb7ea4b4b35f06577180f04abf0addf21a09a2cb339ab36a445177d16a93cb4 0.600000000000 1865285 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": 1377204, "vin": [ { "gen": { "height": 1377194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bb7ea4b4b35f06577180f04abf0addf21a09a2cb339ab36a445177d16a93cb4" } } ], "extra": [ 1, 99, 93, 60, 251, 220, 229, 93, 54, 21, 116, 236, 193, 91, 214, 0, 45, 74, 92, 161, 29, 247, 116, 215, 127, 185, 27, 243, 16, 164, 223, 98, 13, 2, 17, 0, 0, 0, 5, 151, 186, 249, 34, 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