Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91a9e5481ad96f654470cb40a931b85255f8231ca9be4262d8c8f0d33265fdc4

Tx prefix hash: 84d10b10e4a6e3f85c913a70a04738dc804011dbf406ac310067bef61aa01c98
Tx public key: 3acea00dc76ac0e9ff83e972bdae3170c88ea5115b39d166b29ff8aa28f95b44
Timestamp: 1694183178 Timestamp [UCT]: 2023-09-08 14:26:18 Age [y:d:h:m:s]: 01:068:14:11:34
Block: 843709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310294 RingCT/type: yes/0
Extra: 013acea00dc76ac0e9ff83e972bdae3170c88ea5115b39d166b29ff8aa28f95b44021100000004faf35c9c000000000000000000

1 output(s) for total of 0.982747411000 dcy

stealth address amount amount idx
00: e30909f6ec1c3d1034926ba6dfb191a5a1a0b38a227bc7d3d2ba867ece40b808 0.982747411000 1296969 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": 843719, "vin": [ { "gen": { "height": 843709 } } ], "vout": [ { "amount": 982747411, "target": { "key": "e30909f6ec1c3d1034926ba6dfb191a5a1a0b38a227bc7d3d2ba867ece40b808" } } ], "extra": [ 1, 58, 206, 160, 13, 199, 106, 192, 233, 255, 131, 233, 114, 189, 174, 49, 112, 200, 142, 165, 17, 91, 57, 209, 102, 178, 159, 248, 170, 40, 249, 91, 68, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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