Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c2da3c4fdf6c38e0949caf1ffb468dcfcef21d35a1901dbb5f5d526c02c225c

Tx prefix hash: d67636e10bcd9b04b74eb64ac055841cfdb135ba108bf42f71fff0878fc96a3e
Tx public key: 010c491b8dc4859bfde3bb8ab47d60d965c164aff1c1a1be3c87a3fb23a70e1e
Timestamp: 1578454371 Timestamp [UCT]: 2020-01-08 03:32:51 Age [y:d:h:m:s]: 05:105:15:50:38
Block: 40946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1225539 RingCT/type: yes/0
Extra: 01010c491b8dc4859bfde3bb8ab47d60d965c164aff1c1a1be3c87a3fb23a70e1e0211000000138a2ee0d9000000000000000000

1 output(s) for total of 449.086242346000 dcy

stealth address amount amount idx
00: f5c20fce08aa6391f498c71a2cf7196ca119072a17c232d7a63a251450e9c79c 449.086242346000 72452 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": 40956, "vin": [ { "gen": { "height": 40946 } } ], "vout": [ { "amount": 449086242346, "target": { "key": "f5c20fce08aa6391f498c71a2cf7196ca119072a17c232d7a63a251450e9c79c" } } ], "extra": [ 1, 1, 12, 73, 27, 141, 196, 133, 155, 253, 227, 187, 138, 180, 125, 96, 217, 101, 193, 100, 175, 241, 193, 161, 190, 60, 135, 163, 251, 35, 167, 14, 30, 2, 17, 0, 0, 0, 19, 138, 46, 224, 217, 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