Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f16680bbdaa304f66778dd66abde34f0b3442ea2d00cce5c64e092b062ed69ad

Tx prefix hash: 2caeadaf4263600c0700f3542d06ede6211651a624ce8b58ea38b377dc22e61f
Tx public key: 123e6685d9a3c91f692f4a8cb246778c38af39d702968293e9bbedc976d8c3d5
Timestamp: 1717173075 Timestamp [UCT]: 2024-05-31 16:31:15 Age [y:d:h:m:s]: 00:225:08:07:20
Block: 1034122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161263 RingCT/type: yes/0
Extra: 01123e6685d9a3c91f692f4a8cb246778c38af39d702968293e9bbedc976d8c3d502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26d1fa76686abc127e29c9df4965093e20ab563ff4d963e84f26fc91bc1b1f10 0.600000000000 1502601 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": 1034132, "vin": [ { "gen": { "height": 1034122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26d1fa76686abc127e29c9df4965093e20ab563ff4d963e84f26fc91bc1b1f10" } } ], "extra": [ 1, 18, 62, 102, 133, 217, 163, 201, 31, 105, 47, 74, 140, 178, 70, 119, 140, 56, 175, 57, 215, 2, 150, 130, 147, 233, 187, 237, 201, 118, 216, 195, 213, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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