Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b003984be43d133d36ecd8e9b5149ec7f7ac932a68db334f9e232352ddf806bc

Tx prefix hash: bc1287b2b683cf3748b3ccd31b348a46563dc87fed4b5681d5d12dd152bf756f
Tx public key: e7b8bef710b6a6568f6e3daf894f505b47d0e0947dcb70d4c4cc5856df881370
Timestamp: 1724713890 Timestamp [UCT]: 2024-08-26 23:11:30 Age [y:d:h:m:s]: 00:089:06:46:17
Block: 1096628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63862 RingCT/type: yes/0
Extra: 01e7b8bef710b6a6568f6e3daf894f505b47d0e0947dcb70d4c4cc5856df881370021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e1ea44f2b4e5cdf3e3026add21a3f6d7f4bcf65b034a6c01eab161aeb239022 0.600000000000 1571819 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": 1096638, "vin": [ { "gen": { "height": 1096628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e1ea44f2b4e5cdf3e3026add21a3f6d7f4bcf65b034a6c01eab161aeb239022" } } ], "extra": [ 1, 231, 184, 190, 247, 16, 182, 166, 86, 143, 110, 61, 175, 137, 79, 80, 91, 71, 208, 224, 148, 125, 203, 112, 212, 196, 204, 88, 86, 223, 136, 19, 112, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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