Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5a74c79899e25c1b90ddf987e68d07cb0b96af6768f0d5d6f0a22dbe64ef5e2

Tx prefix hash: 1d9929b989b7571b6d60adf0656e38061644c2f57d903d1424b25283889e9c0e
Tx public key: 99781d04b22cfe5af547d13b3f7d5e96dfb9efd099989fa3e60237fd1f11a3e8
Timestamp: 1740682215 Timestamp [UCT]: 2025-02-27 18:50:15 Age [y:d:h:m:s]: 00:222:07:54:07
Block: 1228549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156601 RingCT/type: yes/0
Extra: 0199781d04b22cfe5af547d13b3f7d5e96dfb9efd099989fa3e60237fd1f11a3e80211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28b3f90e9aa6a3983097dc6ce6d1dad296cf4d31d94619101347ad34dd8d97ba 0.600000000000 1715430 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": 1228559, "vin": [ { "gen": { "height": 1228549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28b3f90e9aa6a3983097dc6ce6d1dad296cf4d31d94619101347ad34dd8d97ba" } } ], "extra": [ 1, 153, 120, 29, 4, 178, 44, 254, 90, 245, 71, 209, 59, 63, 125, 94, 150, 223, 185, 239, 208, 153, 152, 159, 163, 230, 2, 55, 253, 31, 17, 163, 232, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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