Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7882b33db35d2e1e7019a63f8117a844b3a61ee837cfde6efb07765d799a6382

Tx prefix hash: 6ea5fbd84e2125055911ab43d512f76147ab7ff7d8d8a77c731b230246fe51d9
Tx public key: 398bba42b031b407991e82daeacd321b23ed07286ce9a3f5cde9dffe9cb533c2
Timestamp: 1712416738 Timestamp [UCT]: 2024-04-06 15:18:58 Age [y:d:h:m:s]: 01:216:06:22:07
Block: 994665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413254 RingCT/type: yes/0
Extra: 01398bba42b031b407991e82daeacd321b23ed07286ce9a3f5cde9dffe9cb533c202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be405a8c6d3800683ebc82d067fee38ed04079d8b0a0dd5aef79f038a99edf11 0.600000000000 1455069 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": 994675, "vin": [ { "gen": { "height": 994665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be405a8c6d3800683ebc82d067fee38ed04079d8b0a0dd5aef79f038a99edf11" } } ], "extra": [ 1, 57, 139, 186, 66, 176, 49, 180, 7, 153, 30, 130, 218, 234, 205, 50, 27, 35, 237, 7, 40, 108, 233, 163, 245, 205, 233, 223, 254, 156, 181, 51, 194, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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