Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 251d3c9ccd68873ca4d919baa88df9dadeffc7b232ca1b9c92092f9de679de71

Tx prefix hash: 0d86dd0b21a10a964690009a2624078edb42cd2714381b0a8befb161489b7c8e
Tx public key: d071417f69d33da22d0c177fb4e88ec3ccb8b07e6b151fcc57a4e2136673ca43
Timestamp: 1703031215 Timestamp [UCT]: 2023-12-20 00:13:35 Age [y:d:h:m:s]: 01:107:16:13:52
Block: 916885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338075 RingCT/type: yes/0
Extra: 01d071417f69d33da22d0c177fb4e88ec3ccb8b07e6b151fcc57a4e2136673ca43021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5023d541d5b6b1c3ab3cc7687b686d1fb6de36eff4de33d47e639632f10447b9 0.600000000000 1374447 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": 916895, "vin": [ { "gen": { "height": 916885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5023d541d5b6b1c3ab3cc7687b686d1fb6de36eff4de33d47e639632f10447b9" } } ], "extra": [ 1, 208, 113, 65, 127, 105, 211, 61, 162, 45, 12, 23, 127, 180, 232, 142, 195, 204, 184, 176, 126, 107, 21, 31, 204, 87, 164, 226, 19, 102, 115, 202, 67, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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