Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 933eb2396a1bd681bed04613cfa9b78335352947f1064fe8e7a6fe1a13b0e86c

Tx prefix hash: 0c93a210fce22ee637ddf83a8200469d057d7d41ae2577e142f3c7c52d149e09
Tx public key: bfbe0f4c93af752e71a126548a2f29fa293be4d0c68c7b621eb6e332409092f7
Timestamp: 1731958495 Timestamp [UCT]: 2024-11-18 19:34:55 Age [y:d:h:m:s]: 01:028:23:25:39
Block: 1156596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279165 RingCT/type: yes/0
Extra: 01bfbe0f4c93af752e71a126548a2f29fa293be4d0c68c7b621eb6e332409092f7021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25096e88f241bd67a616885c3f025ed7d32a62b24210663ccc5bc04671db54f0 0.600000000000 1642219 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": 1156606, "vin": [ { "gen": { "height": 1156596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25096e88f241bd67a616885c3f025ed7d32a62b24210663ccc5bc04671db54f0" } } ], "extra": [ 1, 191, 190, 15, 76, 147, 175, 117, 46, 113, 161, 38, 84, 138, 47, 41, 250, 41, 59, 228, 208, 198, 140, 123, 98, 30, 182, 227, 50, 64, 144, 146, 247, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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