Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e07739674888408eafd4f0c4ef9a600205b8b9718eac851e4c2ab372bc904ecb

Tx prefix hash: 929716b8efe25d0874fc01b1c0235dd695861a2d10a154a9d0482fcb547223a0
Tx public key: 792444895117f504a2a13e0af2c02d3f5b4f5eac2f4ae85f1dd0333715626bb0
Timestamp: 1731429746 Timestamp [UCT]: 2024-11-12 16:42:26 Age [y:d:h:m:s]: 00:192:04:50:31
Block: 1152219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137238 RingCT/type: yes/0
Extra: 01792444895117f504a2a13e0af2c02d3f5b4f5eac2f4ae85f1dd0333715626bb002110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c49505cf429f31d6aac4e99409d598b95cbbae08b7c9032875c2161e8de6fcf 0.600000000000 1637810 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": 1152229, "vin": [ { "gen": { "height": 1152219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c49505cf429f31d6aac4e99409d598b95cbbae08b7c9032875c2161e8de6fcf" } } ], "extra": [ 1, 121, 36, 68, 137, 81, 23, 245, 4, 162, 161, 62, 10, 242, 192, 45, 63, 91, 79, 94, 172, 47, 74, 232, 95, 29, 208, 51, 55, 21, 98, 107, 176, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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