Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b70afcc2e56533639af68411dcfd5e367c1adbc41f1a92527c89e6102b57c5a7

Tx prefix hash: 875b5a22b8d74b9f72df675264e6c3f7f5c69986a42960e321cb4f2e0b9781ba
Tx public key: 0d5bfb8e7fd103ad5bb2c84e16bf409c9b1560cfab477ec68ea78054bffe10e6
Timestamp: 1709019039 Timestamp [UCT]: 2024-02-27 07:30:39 Age [y:d:h:m:s]: 01:267:06:51:44
Block: 966523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449763 RingCT/type: yes/0
Extra: 010d5bfb8e7fd103ad5bb2c84e16bf409c9b1560cfab477ec68ea78054bffe10e60211000000010546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a00d626057528620395331e06b1cef93228bc91cf28ad4aa6f9aed77080b390f 0.600000000000 1426284 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": 966533, "vin": [ { "gen": { "height": 966523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a00d626057528620395331e06b1cef93228bc91cf28ad4aa6f9aed77080b390f" } } ], "extra": [ 1, 13, 91, 251, 142, 127, 209, 3, 173, 91, 178, 200, 78, 22, 191, 64, 156, 155, 21, 96, 207, 171, 71, 126, 198, 142, 167, 128, 84, 191, 254, 16, 230, 2, 17, 0, 0, 0, 1, 5, 70, 215, 208, 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