Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78255fc500240014c15b74f734d0affc59008612f162e9f07c3b349b5ff58578

Tx prefix hash: 7fdf2f2ff97c05abf44da754a0822cc73845e1324afd7a44dcd60fc302ab932c
Tx public key: 34c284d449e107af8b5cb9bfa0833d8e56ba7aa3919612a663a165969c4bcaa5
Timestamp: 1728821876 Timestamp [UCT]: 2024-10-13 12:17:56 Age [y:d:h:m:s]: 00:100:11:47:32
Block: 1130699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71783 RingCT/type: yes/0
Extra: 0134c284d449e107af8b5cb9bfa0833d8e56ba7aa3919612a663a165969c4bcaa5021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5de7bae3c47faf4a749e8b02d3d2f387c0ffbfdaa88ecdc076134c34b98fd6e2 0.600000000000 1613576 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": 1130709, "vin": [ { "gen": { "height": 1130699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5de7bae3c47faf4a749e8b02d3d2f387c0ffbfdaa88ecdc076134c34b98fd6e2" } } ], "extra": [ 1, 52, 194, 132, 212, 73, 225, 7, 175, 139, 92, 185, 191, 160, 131, 61, 142, 86, 186, 122, 163, 145, 150, 18, 166, 99, 161, 101, 150, 156, 75, 202, 165, 2, 17, 0, 0, 0, 9, 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