Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9eb4cc90bd81093e31ae228753047348328e8a1f22941c5fa4a2ac51392e143

Tx prefix hash: d82c31e8147f25d61b84b9c2f4135ca8bfd4c041bee110a343a7d9c0fdd0bf21
Tx public key: 65c7fe40ec9151b7920ed1c50baaf0527e34a03c6c19ad8b809ea2f4694eeed8
Timestamp: 1712621173 Timestamp [UCT]: 2024-04-09 00:06:13 Age [y:d:h:m:s]: 00:322:12:02:44
Block: 996349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230573 RingCT/type: yes/0
Extra: 0165c7fe40ec9151b7920ed1c50baaf0527e34a03c6c19ad8b809ea2f4694eeed802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e38ba3f215ab86b560c3a108c25012a2d0b548e292161068bd39bfd86e9bb8f1 0.600000000000 1456767 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": 996359, "vin": [ { "gen": { "height": 996349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e38ba3f215ab86b560c3a108c25012a2d0b548e292161068bd39bfd86e9bb8f1" } } ], "extra": [ 1, 101, 199, 254, 64, 236, 145, 81, 183, 146, 14, 209, 197, 11, 170, 240, 82, 126, 52, 160, 60, 108, 25, 173, 139, 128, 158, 162, 244, 105, 78, 238, 216, 2, 17, 0, 0, 0, 1, 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