Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96c46be819ef70368b6edffa4483be5469b7f6e18708f003e6dad214b269fa48

Tx prefix hash: 9cb08486086a89ef975a53a85d999d9af4bc671d234be05bf502afc0abc253eb
Tx public key: 0b13a1fab8a8006b003f3ed66e16cdb87a92fd63f8d2387ff7bdd563f08a69c5
Timestamp: 1711935546 Timestamp [UCT]: 2024-04-01 01:39:06 Age [y:d:h:m:s]: 00:301:02:47:19
Block: 990715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215281 RingCT/type: yes/0
Extra: 010b13a1fab8a8006b003f3ed66e16cdb87a92fd63f8d2387ff7bdd563f08a69c50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 062563f1fbaca1a12eac99725c6833fa20c4015c89414343a9d1d494a14d9d1a 0.600000000000 1451041 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": 990725, "vin": [ { "gen": { "height": 990715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "062563f1fbaca1a12eac99725c6833fa20c4015c89414343a9d1d494a14d9d1a" } } ], "extra": [ 1, 11, 19, 161, 250, 184, 168, 0, 107, 0, 63, 62, 214, 110, 22, 205, 184, 122, 146, 253, 99, 248, 210, 56, 127, 247, 189, 213, 99, 240, 138, 105, 197, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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