Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e16d4f39d973ba4d4d275e61d3755f117e6961a14c77db6ab4d81fc32a08b0

Tx prefix hash: 7e3e5118359afdd5a18dcc1a4b521a813d4851dbe572cce813199e1df8d67a77
Tx public key: abeaf14da969686aff7a670e2fa23cd4466ac5d0ee32ae21409d99c0c5de292b
Timestamp: 1709387578 Timestamp [UCT]: 2024-03-02 13:52:58 Age [y:d:h:m:s]: 01:051:04:19:56
Block: 969582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297585 RingCT/type: yes/0
Extra: 01abeaf14da969686aff7a670e2fa23cd4466ac5d0ee32ae21409d99c0c5de292b02110000000d0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6e7d1f88a1ba41d5b51c90e90ab4629f714a26f974a09724426b72f37d39afc 0.600000000000 1429419 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": 969592, "vin": [ { "gen": { "height": 969582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6e7d1f88a1ba41d5b51c90e90ab4629f714a26f974a09724426b72f37d39afc" } } ], "extra": [ 1, 171, 234, 241, 77, 169, 105, 104, 106, 255, 122, 103, 14, 47, 162, 60, 212, 70, 106, 197, 208, 238, 50, 174, 33, 64, 157, 153, 192, 197, 222, 41, 43, 2, 17, 0, 0, 0, 13, 0, 17, 5, 91, 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