Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b580d105316d6fc9cbdc1b2acae6ee250ef6893a5abf86ac410b97731b92dcc

Tx prefix hash: dfa5bf32f067094245495b26014be16aeb2f29afa892266f78a5382ee5e42f42
Tx public key: f6263e5f710c10ed5ff82dd8106d1fb739512e3a1ec9be1aecb29e9b5b655529
Timestamp: 1714920160 Timestamp [UCT]: 2024-05-05 14:42:40 Age [y:d:h:m:s]: 00:335:02:26:46
Block: 1015454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239525 RingCT/type: yes/0
Extra: 01f6263e5f710c10ed5ff82dd8106d1fb739512e3a1ec9be1aecb29e9b5b6555290211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00ae1a2b32140a9bc75669f04f6ab2cfe277b51d2eca93d69077a17303c8636d 0.600000000000 1478819 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": 1015464, "vin": [ { "gen": { "height": 1015454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00ae1a2b32140a9bc75669f04f6ab2cfe277b51d2eca93d69077a17303c8636d" } } ], "extra": [ 1, 246, 38, 62, 95, 113, 12, 16, 237, 95, 248, 45, 216, 16, 109, 31, 183, 57, 81, 46, 58, 30, 201, 190, 26, 236, 178, 158, 155, 91, 101, 85, 41, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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