Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d93a325734e737581f6028bac628744794277eee568587a43b34f783c57ed4e0

Tx prefix hash: c9c0eeb4fcaa82f66e4b3dcdff43f8e8c68b8bd93274edfb90f21d4debecefa7
Tx public key: f884386b1c20e38f96c23c591f47b65789fe3c171407af9005d986dbf92fad42
Timestamp: 1698551051 Timestamp [UCT]: 2023-10-29 03:44:11 Age [y:d:h:m:s]: 01:164:22:08:25
Block: 879950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378865 RingCT/type: yes/0
Extra: 01f884386b1c20e38f96c23c591f47b65789fe3c171407af9005d986dbf92fad42021100000002faf35c9c000000000000000000

1 output(s) for total of 0.745350210000 dcy

stealth address amount amount idx
00: 14c0cb03ff8d0722b928a13b71f411981d59e9112b88a29b76711c56e917de88 0.745350210000 1335490 of 0

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": 879960, "vin": [ { "gen": { "height": 879950 } } ], "vout": [ { "amount": 745350210, "target": { "key": "14c0cb03ff8d0722b928a13b71f411981d59e9112b88a29b76711c56e917de88" } } ], "extra": [ 1, 248, 132, 56, 107, 28, 32, 227, 143, 150, 194, 60, 89, 31, 71, 182, 87, 137, 254, 60, 23, 20, 7, 175, 144, 5, 217, 134, 219, 249, 47, 173, 66, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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