Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ff66755699ea2bbedf6e0d319c2282d749cb2d6797b290d56431061401fc648

Tx prefix hash: ee6fac25e390b597534f60838bc8420cd9b47954f12cce44c88e34c1239c3f43
Tx public key: c3f6f62520d31e5810e3bf2455703f85f25e4ff8f31c8adf68b927bf9de5db1c
Timestamp: 1716318232 Timestamp [UCT]: 2024-05-21 19:03:52 Age [y:d:h:m:s]: 00:247:05:47:19
Block: 1027032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176906 RingCT/type: yes/0
Extra: 01c3f6f62520d31e5810e3bf2455703f85f25e4ff8f31c8adf68b927bf9de5db1c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c693c4cf9d3e54af25f08c4f44613dd225679d7dcd297b78f4a8c2fbfc3f1d1 0.600000000000 1494443 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": 1027042, "vin": [ { "gen": { "height": 1027032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c693c4cf9d3e54af25f08c4f44613dd225679d7dcd297b78f4a8c2fbfc3f1d1" } } ], "extra": [ 1, 195, 246, 246, 37, 32, 211, 30, 88, 16, 227, 191, 36, 85, 112, 63, 133, 242, 94, 79, 248, 243, 28, 138, 223, 104, 185, 39, 191, 157, 229, 219, 28, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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