Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4543f382d64dcbae3baea2d8bc59941a4bfe8fd2081df844c9cfe49f6bb61349

Tx prefix hash: 14d197d05130939b587e3e0295612b7fcdb46f30c501f250f56cd16301626dea
Tx public key: 77f3ec560cf7be0eaa5543d24f7556b6bce0f164db5fdaec91d13b5770491ef3
Timestamp: 1710689677 Timestamp [UCT]: 2024-03-17 15:34:37 Age [y:d:h:m:s]: 01:066:12:21:04
Block: 980386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308541 RingCT/type: yes/0
Extra: 0177f3ec560cf7be0eaa5543d24f7556b6bce0f164db5fdaec91d13b5770491ef30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 697785598c4cb5c0e1390d0d85fbf69ce98256eb6aa68fa6744a54a728c13bc7 0.600000000000 1440451 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": 980396, "vin": [ { "gen": { "height": 980386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "697785598c4cb5c0e1390d0d85fbf69ce98256eb6aa68fa6744a54a728c13bc7" } } ], "extra": [ 1, 119, 243, 236, 86, 12, 247, 190, 14, 170, 85, 67, 210, 79, 117, 86, 182, 188, 224, 241, 100, 219, 95, 218, 236, 145, 209, 59, 87, 112, 73, 30, 243, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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