Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86088ef88bda22a4b6d48c38240b2436b058d8e28f7cb5a8307824e0491648da

Tx prefix hash: 16c598b8e870b59aacb613dc1e6c1d96ab09260408a950ce0d13de2e63751a1e
Tx public key: d7132b8f4303537b6d12631b310749d7fe3c5092e7bd50e1ef0c31dfcd3881e0
Timestamp: 1698388429 Timestamp [UCT]: 2023-10-27 06:33:49 Age [y:d:h:m:s]: 01:167:08:42:17
Block: 878606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380613 RingCT/type: yes/0
Extra: 01d7132b8f4303537b6d12631b310749d7fe3c5092e7bd50e1ef0c31dfcd3881e002110000000433af99f4000000000000000000

1 output(s) for total of 0.753032309000 dcy

stealth address amount amount idx
00: daf13f590277409151af182dc5ada0e963200c8e1cbb098340df14afdfa11641 0.753032309000 1334064 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": 878616, "vin": [ { "gen": { "height": 878606 } } ], "vout": [ { "amount": 753032309, "target": { "key": "daf13f590277409151af182dc5ada0e963200c8e1cbb098340df14afdfa11641" } } ], "extra": [ 1, 215, 19, 43, 143, 67, 3, 83, 123, 109, 18, 99, 27, 49, 7, 73, 215, 254, 60, 80, 146, 231, 189, 80, 225, 239, 12, 49, 223, 205, 56, 129, 224, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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