Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffed92962b9f58f475a0dccb5b3d68be100ca0c4c96905e103b6f5d7da9e4557

Tx prefix hash: 829cc7bee446b80542c09ed3b003dc13936d203856ff5298c5a232c117c28efb
Tx public key: dd9738934bcae16e7b2bf9cefc93e3db7401411910ac59f8a427b89ad7b60c79
Timestamp: 1696051396 Timestamp [UCT]: 2023-09-30 05:23:16 Age [y:d:h:m:s]: 01:105:18:41:54
Block: 859213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336863 RingCT/type: yes/0
Extra: 01dd9738934bcae16e7b2bf9cefc93e3db7401411910ac59f8a427b89ad7b60c7902110000000675e3f0e9000000000000000000

1 output(s) for total of 0.873113489000 dcy

stealth address amount amount idx
00: ed71a3e59717bfc9b41a19c2464706f4ea4f2b312bd06207c63663164c482990 0.873113489000 1313427 of 0

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": 859223, "vin": [ { "gen": { "height": 859213 } } ], "vout": [ { "amount": 873113489, "target": { "key": "ed71a3e59717bfc9b41a19c2464706f4ea4f2b312bd06207c63663164c482990" } } ], "extra": [ 1, 221, 151, 56, 147, 75, 202, 225, 110, 123, 43, 249, 206, 252, 147, 227, 219, 116, 1, 65, 25, 16, 172, 89, 248, 164, 39, 184, 154, 215, 182, 12, 121, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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