Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb134c4df17bf0590de0ea182926ab637fe8636def0ce1400c52f6eccd7a6960

Tx prefix hash: 5c063c78e210df20e18e12931f0580695074fb854ecd4c022a5e426a8e4a9376
Tx public key: 6f9c154143b6d01b618a041cba82fd9d116bbb0c25f9d7502dc2c2c4aab7d6f2
Timestamp: 1710653482 Timestamp [UCT]: 2024-03-17 05:31:22 Age [y:d:h:m:s]: 01:041:09:31:00
Block: 980094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290565 RingCT/type: yes/0
Extra: 016f9c154143b6d01b618a041cba82fd9d116bbb0c25f9d7502dc2c2c4aab7d6f20211000000107a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e4f72350d3bd5b1e7515aedb48fe4aaa2304eec785dbd5168e2e1d138e617d6 0.600000000000 1440153 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": 980104, "vin": [ { "gen": { "height": 980094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e4f72350d3bd5b1e7515aedb48fe4aaa2304eec785dbd5168e2e1d138e617d6" } } ], "extra": [ 1, 111, 156, 21, 65, 67, 182, 208, 27, 97, 138, 4, 28, 186, 130, 253, 157, 17, 107, 187, 12, 37, 249, 215, 80, 45, 194, 194, 196, 170, 183, 214, 242, 2, 17, 0, 0, 0, 16, 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