Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17b2b9b79574a92a1e393362a598b66d79d7441298426c1698954a008c06c212

Tx prefix hash: d7dfbd09b3d79e1f112bf63e24b7670952494f8f04963ec3d68701a61c0e2314
Tx public key: 061aed1b288ec2d8a541e2a3b57c67d29932bba30d3c2ad7fdafb8d9a00f4795
Timestamp: 1698336602 Timestamp [UCT]: 2023-10-26 16:10:02 Age [y:d:h:m:s]: 01:147:09:12:32
Block: 878174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366322 RingCT/type: yes/0
Extra: 01061aed1b288ec2d8a541e2a3b57c67d29932bba30d3c2ad7fdafb8d9a00f47950211000000054b8f5122000000000000000000

1 output(s) for total of 0.755518331000 dcy

stealth address amount amount idx
00: 3cf85d37592475a1b63ac16e1fc9bfec477dc59d7f4a3b1d268bc85615ba8e0a 0.755518331000 1333596 of 0

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": 878184, "vin": [ { "gen": { "height": 878174 } } ], "vout": [ { "amount": 755518331, "target": { "key": "3cf85d37592475a1b63ac16e1fc9bfec477dc59d7f4a3b1d268bc85615ba8e0a" } } ], "extra": [ 1, 6, 26, 237, 27, 40, 142, 194, 216, 165, 65, 226, 163, 181, 124, 103, 210, 153, 50, 187, 163, 13, 60, 42, 215, 253, 175, 184, 217, 160, 15, 71, 149, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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