Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aceb3ab73323cc7788af84c2b8da6f74719b275c1b4b9c1939534bca350b34a5

Tx prefix hash: 0b75810cb3dca6fe3e8b811ff9468cb85724cb3743d092a3b2978b823244fb00
Tx public key: 82437f6fe983326199f98ab64d75a204822755ac82c44b4c9bc9a710bdafc2b8
Timestamp: 1717769285 Timestamp [UCT]: 2024-06-07 14:08:05 Age [y:d:h:m:s]: 00:146:05:21:12
Block: 1039072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104646 RingCT/type: yes/0
Extra: 0182437f6fe983326199f98ab64d75a204822755ac82c44b4c9bc9a710bdafc2b8021100000004d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f636b84f44cfe60dbf97a5ab2603e4b6846705e054dbbf71ae4cf6cb603957e3 0.600000000000 1507661 of 15

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": 1039082, "vin": [ { "gen": { "height": 1039072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f636b84f44cfe60dbf97a5ab2603e4b6846705e054dbbf71ae4cf6cb603957e3" } } ], "extra": [ 1, 130, 67, 127, 111, 233, 131, 50, 97, 153, 249, 138, 182, 77, 117, 162, 4, 130, 39, 85, 172, 130, 196, 75, 76, 155, 201, 167, 16, 189, 175, 194, 184, 2, 17, 0, 0, 0, 4, 215, 73, 245, 17, 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