Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e59ff4f19a5b40f189eb2414ef1e4a44f59b368e92f902caf5a28434a42bb2d

Tx prefix hash: 84b0593cfdca1a7734e4a07af2112dbd89d22d04ed8921b8028e50e439e82081
Tx public key: ffb1ad1cd832f3e9635f1edec3bbefd34ebf474bcdd917325e197d3660d55bd4
Timestamp: 1713941563 Timestamp [UCT]: 2024-04-24 06:52:43 Age [y:d:h:m:s]: 01:055:13:08:59
Block: 1007334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300529 RingCT/type: yes/0
Extra: 01ffb1ad1cd832f3e9635f1edec3bbefd34ebf474bcdd917325e197d3660d55bd40211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48070368c5fabd88a7983daaa1c9481ad746c68e9ffb42c0ecbf68e4df5051e3 0.600000000000 1468638 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": 1007344, "vin": [ { "gen": { "height": 1007334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48070368c5fabd88a7983daaa1c9481ad746c68e9ffb42c0ecbf68e4df5051e3" } } ], "extra": [ 1, 255, 177, 173, 28, 216, 50, 243, 233, 99, 95, 30, 222, 195, 187, 239, 211, 78, 191, 71, 75, 205, 217, 23, 50, 94, 25, 125, 54, 96, 213, 91, 212, 2, 17, 0, 0, 0, 3, 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