Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03c2845182b342158b1d03c1336e00275462d0f345596eee6b3b83cee6b84b9e

Tx prefix hash: 46136c7da12510de2b482e710221e509fe6d8ba7efbeb7c1864dc7c55cb3484b
Tx public key: 94677b35e6dc8daf79746ded899e996d1b85a0d7a04d10b6721f0dbd8032e9e8
Timestamp: 1737372946 Timestamp [UCT]: 2025-01-20 11:35:46 Age [y:d:h:m:s]: 00:152:07:56:51
Block: 1201393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108566 RingCT/type: yes/0
Extra: 0194677b35e6dc8daf79746ded899e996d1b85a0d7a04d10b6721f0dbd8032e9e80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee77043e71d0134887cce04466ce07eea38add221c4465a353cfb0a82d9c95e7 0.600000000000 1688044 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": 1201403, "vin": [ { "gen": { "height": 1201393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee77043e71d0134887cce04466ce07eea38add221c4465a353cfb0a82d9c95e7" } } ], "extra": [ 1, 148, 103, 123, 53, 230, 220, 141, 175, 121, 116, 109, 237, 137, 158, 153, 109, 27, 133, 160, 215, 160, 77, 16, 182, 114, 31, 13, 189, 128, 50, 233, 232, 2, 17, 0, 0, 0, 3, 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