Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a27840173ac1508c1df03d12a9eb43a4659ea9b7e331137361537a7529409bb

Tx prefix hash: 120e13913b637be2f674148214b9c7df81294ac0dd21873a57cb8821feeb1656
Tx public key: 9b44ea9eccbf475d7aa4d63b3120aefe5758636be9f5ac50de99ac84b71522ec
Timestamp: 1726714282 Timestamp [UCT]: 2024-09-19 02:51:22 Age [y:d:h:m:s]: 00:218:20:46:44
Block: 1113218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156239 RingCT/type: yes/0
Extra: 019b44ea9eccbf475d7aa4d63b3120aefe5758636be9f5ac50de99ac84b71522ec02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e48e3e5975baaef7c9d554f75dbb4b081708caa68d056118e39c0c28da91f38 0.600000000000 1592815 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": 1113228, "vin": [ { "gen": { "height": 1113218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e48e3e5975baaef7c9d554f75dbb4b081708caa68d056118e39c0c28da91f38" } } ], "extra": [ 1, 155, 68, 234, 158, 204, 191, 71, 93, 122, 164, 214, 59, 49, 32, 174, 254, 87, 88, 99, 107, 233, 245, 172, 80, 222, 153, 172, 132, 183, 21, 34, 236, 2, 17, 0, 0, 0, 2, 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