Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a04621588242178475ee77b71ed22c1544038d4aac1ab8b1cf7d54fdd7e5acd

Tx prefix hash: 64f263a9502af5aaacde86cad2e76ad502dc2b35a76f54a6ce4ca0bff70c1d36
Tx public key: 7b1fbd6a65c816a7553e206679433802e958a297e9de8ffeb4bedf5708d3c36e
Timestamp: 1608807184 Timestamp [UCT]: 2020-12-24 10:53:04 Age [y:d:h:m:s]: 03:326:14:29:13
Block: 168397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 985514 RingCT/type: yes/0
Extra: 017b1fbd6a65c816a7553e206679433802e958a297e9de8ffeb4bedf5708d3c36e02110000008a4ea414e5000000000000000000

1 output(s) for total of 169.836684163000 dcy

stealth address amount amount idx
00: 4b5b1b1694e4c7a64f86a7ecf226272afd978eaec615e178a7ec9030b4d1c2c5 169.836684163000 312426 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": 168407, "vin": [ { "gen": { "height": 168397 } } ], "vout": [ { "amount": 169836684163, "target": { "key": "4b5b1b1694e4c7a64f86a7ecf226272afd978eaec615e178a7ec9030b4d1c2c5" } } ], "extra": [ 1, 123, 31, 189, 106, 101, 200, 22, 167, 85, 62, 32, 102, 121, 67, 56, 2, 233, 88, 162, 151, 233, 222, 143, 254, 180, 190, 223, 87, 8, 211, 195, 110, 2, 17, 0, 0, 0, 138, 78, 164, 20, 229, 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