Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2b55c5b062ed4b1ed030362451711864f74681557a182a7a97022289dc8af6b

Tx prefix hash: 9d014b410af3ca39e9f454af0074480fa471ed520e153a0e98e6b509d119bb43
Tx public key: caee6488e8b76de065a85afb319c367e13d6f42d86fae576f3a86e58d672043d
Timestamp: 1720542400 Timestamp [UCT]: 2024-07-09 16:26:40 Age [y:d:h:m:s]: 01:129:16:27:20
Block: 1062058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351208 RingCT/type: yes/0
Extra: 01caee6488e8b76de065a85afb319c367e13d6f42d86fae576f3a86e58d672043d02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a01820288bead9c7552a2776838b4f2d4afe00a7363f44841766314f25d45c1 0.600000000000 1532559 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": 1062068, "vin": [ { "gen": { "height": 1062058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a01820288bead9c7552a2776838b4f2d4afe00a7363f44841766314f25d45c1" } } ], "extra": [ 1, 202, 238, 100, 136, 232, 183, 109, 224, 101, 168, 90, 251, 49, 156, 54, 126, 19, 214, 244, 45, 134, 250, 229, 118, 243, 168, 110, 88, 214, 114, 4, 61, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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