Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7cbdeeb9df8ffc4799c30b54ecd951bb5f203b4c8062d9b19dffa07e6686385

Tx prefix hash: efac70ed1156933de297c4725ea96cd5f07dd9094b72e33c96e4e2e378ad864e
Tx public key: 6cf331fb4d9050d3a0c4aeb94f0294099f0aac0cd48693cbcb2bf5c7ab413bd6
Timestamp: 1735729910 Timestamp [UCT]: 2025-01-01 11:11:50 Age [y:d:h:m:s]: 00:115:20:10:51
Block: 1187824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82603 RingCT/type: yes/0
Extra: 016cf331fb4d9050d3a0c4aeb94f0294099f0aac0cd48693cbcb2bf5c7ab413bd60211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3503f83159a1184b853cb1878206e8512a37b82232860734259c65da99a8ba93 0.600000000000 1674321 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": 1187834, "vin": [ { "gen": { "height": 1187824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3503f83159a1184b853cb1878206e8512a37b82232860734259c65da99a8ba93" } } ], "extra": [ 1, 108, 243, 49, 251, 77, 144, 80, 211, 160, 196, 174, 185, 79, 2, 148, 9, 159, 10, 172, 12, 212, 134, 147, 203, 203, 43, 245, 199, 171, 65, 59, 214, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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