Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 223580aa576fabcb786ec036d9ccb0607e61d3e02cee0a61c26801d7ee813e58

Tx prefix hash: cc5b1005666e39353b9141c524ef10a7fba2fa89fb97846c3bbe4fc1fef3fb94
Tx public key: 78047f3840266b62f9609f4be6407052e32d340dac7785b98f7aae6d872459c0
Timestamp: 1736962074 Timestamp [UCT]: 2025-01-15 17:27:54 Age [y:d:h:m:s]: 00:154:07:00:03
Block: 1198022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109986 RingCT/type: yes/0
Extra: 0178047f3840266b62f9609f4be6407052e32d340dac7785b98f7aae6d872459c0021100000009d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5691b60ba095fae71bc411f831c1e3a97c26c0b709854eecd3c380d513d0d03d 0.600000000000 1684639 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": 1198032, "vin": [ { "gen": { "height": 1198022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5691b60ba095fae71bc411f831c1e3a97c26c0b709854eecd3c380d513d0d03d" } } ], "extra": [ 1, 120, 4, 127, 56, 64, 38, 107, 98, 249, 96, 159, 75, 230, 64, 112, 82, 227, 45, 52, 13, 172, 119, 133, 185, 143, 122, 174, 109, 135, 36, 89, 192, 2, 17, 0, 0, 0, 9, 216, 231, 210, 65, 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