Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd93772b5c446b8c10e7f804497d36c28bcb8b9aad48b46446006b5423b4661c

Tx prefix hash: b20bacd4b18aabd36b49c155a135c4bb1643ad1659c9d856fa555ebb535738ca
Tx public key: ea3b5b587380124c088a59c5b9d687f08f241e7c27a3ffc035d07c319cd9a9bd
Timestamp: 1728125200 Timestamp [UCT]: 2024-10-05 10:46:40 Age [y:d:h:m:s]: 00:182:13:55:34
Block: 1124916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130283 RingCT/type: yes/0
Extra: 01ea3b5b587380124c088a59c5b9d687f08f241e7c27a3ffc035d07c319cd9a9bd02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad563b2c2bbecf288105a3da56d7b5cac86815ec90920c17264c9ba6fb8ed635 0.600000000000 1607589 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": 1124926, "vin": [ { "gen": { "height": 1124916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad563b2c2bbecf288105a3da56d7b5cac86815ec90920c17264c9ba6fb8ed635" } } ], "extra": [ 1, 234, 59, 91, 88, 115, 128, 18, 76, 8, 138, 89, 197, 185, 214, 135, 240, 143, 36, 30, 124, 39, 163, 255, 192, 53, 208, 124, 49, 156, 217, 169, 189, 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