Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3bbec5ddda13e214d67ffaf06e9ff28d7afb8c70d0d651970386f28c09e35be

Tx prefix hash: 46fe69dafaef4ba951ef989b359ae0b1ec22c2646e99b9dbf5f035e080354c5a
Tx public key: 4702386bace8d22c9a40306ce9f1bee17dc1c38d791a86694f0628b175a4e693
Timestamp: 1726000909 Timestamp [UCT]: 2024-09-10 20:41:49 Age [y:d:h:m:s]: 00:206:12:07:30
Block: 1107305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147433 RingCT/type: yes/0
Extra: 014702386bace8d22c9a40306ce9f1bee17dc1c38d791a86694f0628b175a4e69302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8711f641281d5e0da2ef48be064c2337abc33f5ae38387c1f1e1521e641046e0 0.600000000000 1584916 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": 1107315, "vin": [ { "gen": { "height": 1107305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8711f641281d5e0da2ef48be064c2337abc33f5ae38387c1f1e1521e641046e0" } } ], "extra": [ 1, 71, 2, 56, 107, 172, 232, 210, 44, 154, 64, 48, 108, 233, 241, 190, 225, 125, 193, 195, 141, 121, 26, 134, 105, 79, 6, 40, 177, 117, 164, 230, 147, 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