Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1ae9284d9e772bb4133ed75c9f17eea20709736e103aca13450a1b4d3b75c53

Tx prefix hash: ebf51c09af4684e7011ee477d6abf2e87b7b7cc6f58337ed06dd0c1f80c0dee8
Tx public key: dacf4121e84bd30e2d220985230e4f45a57a97ac835737ed0c0fc49f7d9ec8f6
Timestamp: 1712270587 Timestamp [UCT]: 2024-04-04 22:43:07 Age [y:d:h:m:s]: 01:213:07:32:35
Block: 993456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411147 RingCT/type: yes/0
Extra: 01dacf4121e84bd30e2d220985230e4f45a57a97ac835737ed0c0fc49f7d9ec8f60211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0a8b355c1484a7dbee311be3c4bdf1d90c1cbd8c16d6216f0e399828e5df1db 0.600000000000 1453842 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": 993466, "vin": [ { "gen": { "height": 993456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0a8b355c1484a7dbee311be3c4bdf1d90c1cbd8c16d6216f0e399828e5df1db" } } ], "extra": [ 1, 218, 207, 65, 33, 232, 75, 211, 14, 45, 34, 9, 133, 35, 14, 79, 69, 165, 122, 151, 172, 131, 87, 55, 237, 12, 15, 196, 159, 125, 158, 200, 246, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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