Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1daf622d3173d37b5a7140bf711ff56d0fff6fb86e1557e6736254c88563068

Tx prefix hash: 3964e9132f4c1e820adf0ee61aae783de51d6c7374edca5e528ae85bb16ec82e
Tx public key: 16d8f887f6c283f885402c1a708e5255a1cbf73c8203be8c9448942ed1143a70
Timestamp: 1704560508 Timestamp [UCT]: 2024-01-06 17:01:48 Age [y:d:h:m:s]: 01:161:21:16:25
Block: 929540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376745 RingCT/type: yes/0
Extra: 0116d8f887f6c283f885402c1a708e5255a1cbf73c8203be8c9448942ed1143a7002110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85e73687e63e5f4fa5c017f476e19f9a67ea2951cf8e936ba13ac01b449fe1d1 0.600000000000 1387416 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": 929550, "vin": [ { "gen": { "height": 929540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85e73687e63e5f4fa5c017f476e19f9a67ea2951cf8e936ba13ac01b449fe1d1" } } ], "extra": [ 1, 22, 216, 248, 135, 246, 194, 131, 248, 133, 64, 44, 26, 112, 142, 82, 85, 161, 203, 247, 60, 130, 3, 190, 140, 148, 72, 148, 46, 209, 20, 58, 112, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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