Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09dd7b8ab11dc1e8c07bba7b7959db91e7c2a58f6bdb0d246a99f54707da8633

Tx prefix hash: d86850a187a8658a99708fcef30e17f483ec41d1daf2aa81e45a7e3559ca25f7
Tx public key: f376bfbfa06bfb0f70b0a29c6f8df5f29e1a9206e0edd7bc4cf35e03f0b1f036
Timestamp: 1708322212 Timestamp [UCT]: 2024-02-19 05:56:52 Age [y:d:h:m:s]: 01:115:02:56:25
Block: 960739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343304 RingCT/type: yes/0
Extra: 01f376bfbfa06bfb0f70b0a29c6f8df5f29e1a9206e0edd7bc4cf35e03f0b1f03602110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebc920db1ff11629cf15c35d9ab5fa6cb89487e8cf24d0ba6f794f71e89d3068 0.600000000000 1420326 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": 960749, "vin": [ { "gen": { "height": 960739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebc920db1ff11629cf15c35d9ab5fa6cb89487e8cf24d0ba6f794f71e89d3068" } } ], "extra": [ 1, 243, 118, 191, 191, 160, 107, 251, 15, 112, 176, 162, 156, 111, 141, 245, 242, 158, 26, 146, 6, 224, 237, 215, 188, 76, 243, 94, 3, 240, 177, 240, 54, 2, 17, 0, 0, 0, 8, 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