Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d33049f4aaa50a8b24e3430949a257810cceae7101fa0f17366474958f94c041

Tx prefix hash: 5f9e0f5be578501e73f79e388247d69fa3c0510adf3ea55d9d8bb52de9c9e085
Tx public key: cfa409f4437c9217298e89c7e51a8cfa7e16ea7d86f129ec5842a4d2787d8349
Timestamp: 1716024458 Timestamp [UCT]: 2024-05-18 09:27:38 Age [y:d:h:m:s]: 01:174:06:24:04
Block: 1024600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383147 RingCT/type: yes/0
Extra: 01cfa409f4437c9217298e89c7e51a8cfa7e16ea7d86f129ec5842a4d2787d83490211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b39a3cf360a168fe8c24e42af4c97d925eff28292c7b2f7582d9074187acec0f 0.600000000000 1490463 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": 1024610, "vin": [ { "gen": { "height": 1024600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b39a3cf360a168fe8c24e42af4c97d925eff28292c7b2f7582d9074187acec0f" } } ], "extra": [ 1, 207, 164, 9, 244, 67, 124, 146, 23, 41, 142, 137, 199, 229, 26, 140, 250, 126, 22, 234, 125, 134, 241, 41, 236, 88, 66, 164, 210, 120, 125, 131, 73, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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