Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4cf317db0fb8f1911f7681a065fe2f0a26c6503d7846ac6d7ee70c5f93bce58

Tx prefix hash: c5ec0a0057babe6f30529142be291cc204edb040d7fcec4e3452cb7ce75411fc
Tx public key: d1291a63572466cd5cf37f4738201ed797f1dc6dae7ed4154957fd2b146fb035
Timestamp: 1711422177 Timestamp [UCT]: 2024-03-26 03:02:57 Age [y:d:h:m:s]: 00:289:01:49:48
Block: 986465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206897 RingCT/type: yes/0
Extra: 01d1291a63572466cd5cf37f4738201ed797f1dc6dae7ed4154957fd2b146fb03502110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac1ea5c99ae86c87ffdba8798582d1194b97a576faafd7aafe7e1e068b8c0bfe 0.600000000000 1446694 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": 986475, "vin": [ { "gen": { "height": 986465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac1ea5c99ae86c87ffdba8798582d1194b97a576faafd7aafe7e1e068b8c0bfe" } } ], "extra": [ 1, 209, 41, 26, 99, 87, 36, 102, 205, 92, 243, 127, 71, 56, 32, 30, 215, 151, 241, 220, 109, 174, 126, 212, 21, 73, 87, 253, 43, 20, 111, 176, 53, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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