Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acc0ce628792cdd6f6eb75fd52f8230c6f1093cefa3782ee1f36b519d192a59c

Tx prefix hash: 65fe06a8250bf6403e9580f01341cd0ba392a664e104cd24866bf9483170b3d5
Tx public key: 48ff560e01f52df6128e1887d989b7d649e2989f445bcc36859e4b9c5ccf3a33
Timestamp: 1724096857 Timestamp [UCT]: 2024-08-19 19:47:37 Age [y:d:h:m:s]: 00:252:23:14:06
Block: 1091528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180679 RingCT/type: yes/0
Extra: 0148ff560e01f52df6128e1887d989b7d649e2989f445bcc36859e4b9c5ccf3a3302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24d03b6720d9086471e4518f71b9a7d819a482efdeaef9c4c5fccf3c4fe0d5e8 0.600000000000 1566161 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": 1091538, "vin": [ { "gen": { "height": 1091528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24d03b6720d9086471e4518f71b9a7d819a482efdeaef9c4c5fccf3c4fe0d5e8" } } ], "extra": [ 1, 72, 255, 86, 14, 1, 245, 45, 246, 18, 142, 24, 135, 217, 137, 183, 214, 73, 226, 152, 159, 68, 91, 204, 54, 133, 158, 75, 156, 92, 207, 58, 51, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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