Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 309e63090b8c7afcfc7b569bc4353a0266382ab3eb5698141fc5ce15656af3cb

Tx prefix hash: 6b4acf13ebd3016ce3a19bc26f2e4058bce4ff48544d290d6c0502332fba4eeb
Tx public key: ad7412e01970bcc7e5e40b4fc9e5db55260ec5cb989e9f6fd6e468dc7e09870c
Timestamp: 1718211499 Timestamp [UCT]: 2024-06-12 16:58:19 Age [y:d:h:m:s]: 01:151:02:46:25
Block: 1042730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366567 RingCT/type: yes/0
Extra: 01ad7412e01970bcc7e5e40b4fc9e5db55260ec5cb989e9f6fd6e468dc7e09870c0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed1748c8d4d9a44d536253d22e7e60bfa849b8bfecf8b5a6596e06686a598776 0.600000000000 1511717 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": 1042740, "vin": [ { "gen": { "height": 1042730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed1748c8d4d9a44d536253d22e7e60bfa849b8bfecf8b5a6596e06686a598776" } } ], "extra": [ 1, 173, 116, 18, 224, 25, 112, 188, 199, 229, 228, 11, 79, 201, 229, 219, 85, 38, 14, 197, 203, 152, 158, 159, 111, 214, 228, 104, 220, 126, 9, 135, 12, 2, 17, 0, 0, 0, 5, 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