Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0f7f018bade0ed667ed4c97d5d730724220d08700071f8d1a7aa2464ec9d915

Tx prefix hash: b411c6712fc349b11a799d37ca4c7a566854fcfe3ba00087d213d9b2642d0b49
Tx public key: 9d9471ded697a0a4b233290e6f9e9b5b11be6972b4a50e0764a65f679a731513
Timestamp: 1722091426 Timestamp [UCT]: 2024-07-27 14:43:46 Age [y:d:h:m:s]: 00:313:03:52:03
Block: 1074895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223767 RingCT/type: yes/0
Extra: 019d9471ded697a0a4b233290e6f9e9b5b11be6972b4a50e0764a65f679a731513021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17561d733b5e011a6576e20a86aa31f80340909081ac7b0843c9b732b3f9be0a 0.600000000000 1547414 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": 1074905, "vin": [ { "gen": { "height": 1074895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17561d733b5e011a6576e20a86aa31f80340909081ac7b0843c9b732b3f9be0a" } } ], "extra": [ 1, 157, 148, 113, 222, 214, 151, 160, 164, 178, 51, 41, 14, 111, 158, 155, 91, 17, 190, 105, 114, 180, 165, 14, 7, 100, 166, 95, 103, 154, 115, 21, 19, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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