Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12313eff5968e080a4f2306daafad34413f76105401675b09c77eea7b8305468

Tx prefix hash: 8937653dc300b1af1298e7b92af0a6fa3ea75eb09e66649f9156ef2ead4ca8bc
Tx public key: a462e2bb3b46f9e4a9880289f9c1dbff85cbbfd99f6bd511004f7b44c347526e
Timestamp: 1713629473 Timestamp [UCT]: 2024-04-20 16:11:13 Age [y:d:h:m:s]: 00:355:05:24:05
Block: 1004727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253958 RingCT/type: yes/0
Extra: 01a462e2bb3b46f9e4a9880289f9c1dbff85cbbfd99f6bd511004f7b44c347526e0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acf342ca1da4e9f9b4514637c8b7b2ab3c38206690a361e41fd443e8d16c0580 0.600000000000 1465299 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": 1004737, "vin": [ { "gen": { "height": 1004727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acf342ca1da4e9f9b4514637c8b7b2ab3c38206690a361e41fd443e8d16c0580" } } ], "extra": [ 1, 164, 98, 226, 187, 59, 70, 249, 228, 169, 136, 2, 137, 249, 193, 219, 255, 133, 203, 191, 217, 159, 107, 213, 17, 0, 79, 123, 68, 195, 71, 82, 110, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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