Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fed1c15e43c8e0fbc729ccf7b2fa05938fef1ca6fa095e77bf3841fca89a638

Tx prefix hash: 50196b8358c629dd99599c6af9b9c05f6b8ced04a1ec6539c86cc85e51b9fc04
Tx public key: f670a22116382c0f7ed6737ec8af6eb3cd43c7173608b4e560bf76355c4c0b7e
Timestamp: 1708750043 Timestamp [UCT]: 2024-02-24 04:47:23 Age [y:d:h:m:s]: 01:049:04:19:09
Block: 964288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296176 RingCT/type: yes/0
Extra: 01f670a22116382c0f7ed6737ec8af6eb3cd43c7173608b4e560bf76355c4c0b7e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64634cf2b1fc96677a07e689e6c2ce6f07630db15481364cfd3e92fce2d489b8 0.600000000000 1424019 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": 964298, "vin": [ { "gen": { "height": 964288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64634cf2b1fc96677a07e689e6c2ce6f07630db15481364cfd3e92fce2d489b8" } } ], "extra": [ 1, 246, 112, 162, 33, 22, 56, 44, 15, 126, 214, 115, 126, 200, 175, 110, 179, 205, 67, 199, 23, 54, 8, 180, 229, 96, 191, 118, 53, 92, 76, 11, 126, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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