Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4383063e757ae2a34d97fb921d8443ae0f816d22b4093b6bde0b6fa01aed0365

Tx prefix hash: a93591e9b3a64cdcc5891b185c5dbb29a1e7013bc9d8f6324d416aa3c2ff706d
Tx public key: f210a065c1e5e5de01303f088bda6a6cbc1c8bfc9a63031905053ec9ef77fe20
Timestamp: 1703256710 Timestamp [UCT]: 2023-12-22 14:51:50 Age [y:d:h:m:s]: 01:143:00:24:04
Block: 918744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363357 RingCT/type: yes/0
Extra: 01f210a065c1e5e5de01303f088bda6a6cbc1c8bfc9a63031905053ec9ef77fe2002110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8729d90a4f195365d41e2f7ef882b750834ce9c680d6b905e4976b2a29dfddd2 0.600000000000 1376402 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": 918754, "vin": [ { "gen": { "height": 918744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8729d90a4f195365d41e2f7ef882b750834ce9c680d6b905e4976b2a29dfddd2" } } ], "extra": [ 1, 242, 16, 160, 101, 193, 229, 229, 222, 1, 48, 63, 8, 139, 218, 106, 108, 188, 28, 139, 252, 154, 99, 3, 25, 5, 5, 62, 201, 239, 119, 254, 32, 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