Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e787deca52db7027f42eea8760e70e59cc3de22f596c423984e4fea033f22ea

Tx prefix hash: d9cc062fffc4c239e3236afedafdf0231b35e761610e8468de442d839d9f9341
Tx public key: 0fc4c9f97202125aeb6639faff7d2454508cedc919dc6aa80d4901c77a55a191
Timestamp: 1725141763 Timestamp [UCT]: 2024-08-31 22:02:43 Age [y:d:h:m:s]: 00:273:13:37:01
Block: 1100177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195424 RingCT/type: yes/0
Extra: 010fc4c9f97202125aeb6639faff7d2454508cedc919dc6aa80d4901c77a55a19102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bfb060996eabfd330b4d86e6e090928e2c07b176a5b9924cf2d4a7283d8f07a 0.600000000000 1576150 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": 1100187, "vin": [ { "gen": { "height": 1100177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bfb060996eabfd330b4d86e6e090928e2c07b176a5b9924cf2d4a7283d8f07a" } } ], "extra": [ 1, 15, 196, 201, 249, 114, 2, 18, 90, 235, 102, 57, 250, 255, 125, 36, 84, 80, 140, 237, 201, 25, 220, 106, 168, 13, 73, 1, 199, 122, 85, 161, 145, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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