Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b99ad47b900a080abf223efc5b7b32f00a2799efe32d07948a2c9b549336bb7e

Tx prefix hash: 72a1b5a2c5778f56d5beeac332a007c26bf7744db0e6cc049947922b2b25fcff
Tx public key: 872ab2f4c8917d134ac1459bffd6bc4ef5ea2ed2b5e3050cc9e83dca9a9c0eeb
Timestamp: 1630936097 Timestamp [UCT]: 2021-09-06 13:48:17 Age [y:d:h:m:s]: 03:158:00:51:55
Block: 328564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 887715 RingCT/type: yes/0
Extra: 01872ab2f4c8917d134ac1459bffd6bc4ef5ea2ed2b5e3050cc9e83dca9a9c0eeb02110000001851fa4013000000000000000000

1 output(s) for total of 50.041638730000 dcy

stealth address amount amount idx
00: 4cb1d3fbaeea6404db33aeabf1eb47ffbe330c74c3e0b9eed617a10ad7994162 50.041638730000 680007 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": 328574, "vin": [ { "gen": { "height": 328564 } } ], "vout": [ { "amount": 50041638730, "target": { "key": "4cb1d3fbaeea6404db33aeabf1eb47ffbe330c74c3e0b9eed617a10ad7994162" } } ], "extra": [ 1, 135, 42, 178, 244, 200, 145, 125, 19, 74, 193, 69, 155, 255, 214, 188, 78, 245, 234, 46, 210, 181, 227, 5, 12, 201, 232, 61, 202, 154, 156, 14, 235, 2, 17, 0, 0, 0, 24, 81, 250, 64, 19, 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