Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbe2fcf5dc806f2bf8237ca2d9d2be101cf93727803c81220b17c081b39843f1

Tx prefix hash: 9f13265c435f4aec45d831b59d1135c6827883ee851e4b8f696a763b67c84640
Tx public key: 0f0bf2f2fc289e50885e35fdea1108189399d007d3bca537c2f6b3b66154e15d
Timestamp: 1720651557 Timestamp [UCT]: 2024-07-10 22:45:57 Age [y:d:h:m:s]: 00:184:20:58:48
Block: 1062961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132268 RingCT/type: yes/0
Extra: 010f0bf2f2fc289e50885e35fdea1108189399d007d3bca537c2f6b3b66154e15d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b373caca8919a8db832a9a642d20859c0c2a229af1449e0a03b96ac91805d32a 0.600000000000 1533472 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": 1062971, "vin": [ { "gen": { "height": 1062961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b373caca8919a8db832a9a642d20859c0c2a229af1449e0a03b96ac91805d32a" } } ], "extra": [ 1, 15, 11, 242, 242, 252, 40, 158, 80, 136, 94, 53, 253, 234, 17, 8, 24, 147, 153, 208, 7, 211, 188, 165, 55, 194, 246, 179, 182, 97, 84, 225, 93, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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