Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0830c20bace4683bfd794565b40a10d31e9272f18c166dbc9d043e17619f3f16

Tx prefix hash: 5481715ddb16ea6df4ef91eb24579e56aca0a0ad1c2e08119eba027153010f74
Tx public key: b0bd51303703c8e8436d4e902f22e554ae3d94bc31911648ba74b06d8aed1b18
Timestamp: 1675369594 Timestamp [UCT]: 2023-02-02 20:26:34 Age [y:d:h:m:s]: 02:087:07:05:59
Block: 688424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 584041 RingCT/type: yes/0
Extra: 01b0bd51303703c8e8436d4e902f22e554ae3d94bc31911648ba74b06d8aed1b180211000000018b7b6602000000000000000000

1 output(s) for total of 3.213404813000 dcy

stealth address amount amount idx
00: 0994b0070644edbd235853d7830e88d2d0ee8427a3f158b0c2ee78beea1d2e5e 3.213404813000 1131042 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": 688434, "vin": [ { "gen": { "height": 688424 } } ], "vout": [ { "amount": 3213404813, "target": { "key": "0994b0070644edbd235853d7830e88d2d0ee8427a3f158b0c2ee78beea1d2e5e" } } ], "extra": [ 1, 176, 189, 81, 48, 55, 3, 200, 232, 67, 109, 78, 144, 47, 34, 229, 84, 174, 61, 148, 188, 49, 145, 22, 72, 186, 116, 176, 109, 138, 237, 27, 24, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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