Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b39f919173c52752e875b2613cca354270e3cbebd3d82091a1339ed516dbf50a

Tx prefix hash: 62abf1c304c11eca32037cb9fdd1b58cb047f3c1bac92066c5e040637a9a7314
Tx public key: 287010468e3e0c8746f599666dd22e82b1d75cddd10d0c5dece396fc2a0f1d7f
Timestamp: 1712740159 Timestamp [UCT]: 2024-04-10 09:09:19 Age [y:d:h:m:s]: 00:357:08:14:06
Block: 997348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255489 RingCT/type: yes/0
Extra: 01287010468e3e0c8746f599666dd22e82b1d75cddd10d0c5dece396fc2a0f1d7f021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4468e202a5ae9ffe98546d534ac664d24b366e286679aa3314006559f1fa47ab 0.600000000000 1457778 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": 997358, "vin": [ { "gen": { "height": 997348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4468e202a5ae9ffe98546d534ac664d24b366e286679aa3314006559f1fa47ab" } } ], "extra": [ 1, 40, 112, 16, 70, 142, 62, 12, 135, 70, 245, 153, 102, 109, 210, 46, 130, 177, 215, 92, 221, 209, 13, 12, 93, 236, 227, 150, 252, 42, 15, 29, 127, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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