Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2884d117d283b60fd2a910d76bfd1f7db306e68534a7f2111b891330aa530518

Tx prefix hash: dd42b3b3f82bc037d765dceb197800dbee4bb07a1910397ee8bbfafa7488667c
Tx public key: 29d98fcdd19d01dd18253a0fc09a0d38669bae0852cea064a115c817cf524774
Timestamp: 1705982677 Timestamp [UCT]: 2024-01-23 04:04:37 Age [y:d:h:m:s]: 01:296:12:27:11
Block: 941316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470741 RingCT/type: yes/0
Extra: 0129d98fcdd19d01dd18253a0fc09a0d38669bae0852cea064a115c817cf5247740211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e95dc9b44b74b628a69b08c189ba6d2b5c40d5846397ee7fce7aa1b631a8d3f 0.600000000000 1399462 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": 941326, "vin": [ { "gen": { "height": 941316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e95dc9b44b74b628a69b08c189ba6d2b5c40d5846397ee7fce7aa1b631a8d3f" } } ], "extra": [ 1, 41, 217, 143, 205, 209, 157, 1, 221, 24, 37, 58, 15, 192, 154, 13, 56, 102, 155, 174, 8, 82, 206, 160, 100, 161, 21, 200, 23, 207, 82, 71, 116, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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