Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c59e8d7f801689fe47b171dcc088e6662b664516e21d2edb9eff3f86c199d307

Tx prefix hash: 072fa32cd8cd7a416fe6daceef676b12f1c7d139f585be0550fb6de57f501485
Tx public key: 7aca00e35843a0ed15e541e506176b70fa906c8b35efb6e8fac24808fdecce66
Timestamp: 1696090436 Timestamp [UCT]: 2023-09-30 16:13:56 Age [y:d:h:m:s]: 01:121:07:30:40
Block: 859539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347722 RingCT/type: yes/0
Extra: 017aca00e35843a0ed15e541e506176b70fa906c8b35efb6e8fac24808fdecce66021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.870944586000 dcy

stealth address amount amount idx
00: 71a3dd35a854896f1cecc7d1914fa0c92fdc29d641dd2d21871e620de1cc7664 0.870944586000 1313769 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": 859549, "vin": [ { "gen": { "height": 859539 } } ], "vout": [ { "amount": 870944586, "target": { "key": "71a3dd35a854896f1cecc7d1914fa0c92fdc29d641dd2d21871e620de1cc7664" } } ], "extra": [ 1, 122, 202, 0, 227, 88, 67, 160, 237, 21, 229, 65, 229, 6, 23, 107, 112, 250, 144, 108, 139, 53, 239, 182, 232, 250, 194, 72, 8, 253, 236, 206, 102, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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