Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05d757ab4ca7b9b4f3cd89ce5f5a231f61f9488943ca830b4ecf0fd31231ead4

Tx prefix hash: 8e67a87f0cb7178fa7f05c430b4371e714bea58c40c0b650c8a8c66ea3672710
Tx public key: 7cab5fc27d852f75ced347e985b55ec87c5417e76d5711d851e8ef33b163bc93
Timestamp: 1733464998 Timestamp [UCT]: 2024-12-06 06:03:18 Age [y:d:h:m:s]: 00:124:12:28:23
Block: 1169084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88792 RingCT/type: yes/0
Extra: 017cab5fc27d852f75ced347e985b55ec87c5417e76d5711d851e8ef33b163bc930211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f8cfb658eaebb0b0935a656fa24b6e18c14c91e1fa5bf2a349d9015829665b9 0.600000000000 1654797 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": 1169094, "vin": [ { "gen": { "height": 1169084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f8cfb658eaebb0b0935a656fa24b6e18c14c91e1fa5bf2a349d9015829665b9" } } ], "extra": [ 1, 124, 171, 95, 194, 125, 133, 47, 117, 206, 211, 71, 233, 133, 181, 94, 200, 124, 84, 23, 231, 109, 87, 17, 216, 81, 232, 239, 51, 177, 99, 188, 147, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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