Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1d18d9ae4032f1512bd1c9b27cb13446f7ceed664aebc97fe7426ccf066f46

Tx prefix hash: 47129b0166dfbfaabd5466da0fa9134e046aa97a9cde06e59303e40e6977d329
Tx public key: af719a68dc2ea61efa6870a335db70b506001dfb4dfc77bb3fd6e8f9858a4b5c
Timestamp: 1711305280 Timestamp [UCT]: 2024-03-24 18:34:40 Age [y:d:h:m:s]: 01:081:16:27:29
Block: 985490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319305 RingCT/type: yes/0
Extra: 01af719a68dc2ea61efa6870a335db70b506001dfb4dfc77bb3fd6e8f9858a4b5c0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6fdff18f5aac83096eaa57fa742496b880e419ea7537c054c0bb5a2bec04467 0.600000000000 1445703 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": 985500, "vin": [ { "gen": { "height": 985490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6fdff18f5aac83096eaa57fa742496b880e419ea7537c054c0bb5a2bec04467" } } ], "extra": [ 1, 175, 113, 154, 104, 220, 46, 166, 30, 250, 104, 112, 163, 53, 219, 112, 181, 6, 0, 29, 251, 77, 252, 119, 187, 63, 214, 232, 249, 133, 138, 75, 92, 2, 17, 0, 0, 0, 4, 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