Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d2953842a30f794b7b9cfd91e426f827d6625b44e7976a95fa3e2fe251ec8cb

Tx prefix hash: 5e59ab2d9baf0aeb7f0f1aeb8ad8a016e64ad391211efa00ba0d3e979bd449e8
Tx public key: f3d6c45e84453c0c9295011018153ae9913ee51ef35f4d2ab3d03878e31ab2a7
Timestamp: 1673965850 Timestamp [UCT]: 2023-01-17 14:30:50 Age [y:d:h:m:s]: 02:298:05:45:42
Block: 676768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 732541 RingCT/type: yes/0
Extra: 01f3d6c45e84453c0c9295011018153ae9913ee51ef35f4d2ab3d03878e31ab2a70211000000025ec35160000000000000000000

1 output(s) for total of 3.512259724000 dcy

stealth address amount amount idx
00: c9373ad8d2a74e34d27a42c6cfb5ac342c96d4bfe5ff7183dc1774e2c736ecd3 3.512259724000 1118497 of 0

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": 676778, "vin": [ { "gen": { "height": 676768 } } ], "vout": [ { "amount": 3512259724, "target": { "key": "c9373ad8d2a74e34d27a42c6cfb5ac342c96d4bfe5ff7183dc1774e2c736ecd3" } } ], "extra": [ 1, 243, 214, 196, 94, 132, 69, 60, 12, 146, 149, 1, 16, 24, 21, 58, 233, 145, 62, 229, 30, 243, 95, 77, 42, 179, 208, 56, 120, 227, 26, 178, 167, 2, 17, 0, 0, 0, 2, 94, 195, 81, 96, 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