Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 437e2b3d7737050887e4dc58ca6d0d529964b1d4ae58212fc7d1b93698903c0c

Tx prefix hash: 8329ad9594dc0a2e05f1f5ccf1d2b13f2551585cba1ddaaa72ec36e7a9f2b1b8
Tx public key: 6a48ea0795d4089e4722d31c56f2cc33e84682e54c05bac3773626d4b1d8239a
Timestamp: 1583908806 Timestamp [UCT]: 2020-03-11 06:40:06 Age [y:d:h:m:s]: 05:063:07:31:09
Block: 80296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201060 RingCT/type: yes/0
Extra: 016a48ea0795d4089e4722d31c56f2cc33e84682e54c05bac3773626d4b1d8239a0211000000128a2ee0d9000000000000000000

1 output(s) for total of 332.618812754000 dcy

stealth address amount amount idx
00: 5c45be996ae11e8d40d0ac1fec9e1fc7f8cbf28399fedb7590d1e17403b3f7bc 332.618812754000 146986 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": 80306, "vin": [ { "gen": { "height": 80296 } } ], "vout": [ { "amount": 332618812754, "target": { "key": "5c45be996ae11e8d40d0ac1fec9e1fc7f8cbf28399fedb7590d1e17403b3f7bc" } } ], "extra": [ 1, 106, 72, 234, 7, 149, 212, 8, 158, 71, 34, 211, 28, 86, 242, 204, 51, 232, 70, 130, 229, 76, 5, 186, 195, 119, 54, 38, 212, 177, 216, 35, 154, 2, 17, 0, 0, 0, 18, 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