Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60dab9bab14e97fa4f2516f14457e51ceedd21cec4811006ebe447aa73a1e9e5

Tx prefix hash: bb1fddc50e8a5ef83b2c9e4d58b124c5e3e4176525bbf219e45412a2291a1888
Tx public key: d833de0ae7b332392ff08fad601d096d42721a10ee04a08e0e24271a9161d2ce
Timestamp: 1643300659 Timestamp [UCT]: 2022-01-27 16:24:19 Age [y:d:h:m:s]: 02:347:02:00:30
Block: 426454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 766606 RingCT/type: yes/0
Extra: 01d833de0ae7b332392ff08fad601d096d42721a10ee04a08e0e24271a9161d2ce021100000001c9993c7f000000000000000000

1 output(s) for total of 23.712709550000 dcy

stealth address amount amount idx
00: 660d8ed92ed9bffa65782177d994621fd18c0625bdf31cb370fde468f6346cf3 23.712709550000 835287 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": 426464, "vin": [ { "gen": { "height": 426454 } } ], "vout": [ { "amount": 23712709550, "target": { "key": "660d8ed92ed9bffa65782177d994621fd18c0625bdf31cb370fde468f6346cf3" } } ], "extra": [ 1, 216, 51, 222, 10, 231, 179, 50, 57, 47, 240, 143, 173, 96, 29, 9, 109, 66, 114, 26, 16, 238, 4, 160, 142, 14, 36, 39, 26, 145, 97, 210, 206, 2, 17, 0, 0, 0, 1, 201, 153, 60, 127, 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