Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 601894414707876079efcaf70bf3a1e20ff66f7ee07a3bb560907bef5f1220ff

Tx prefix hash: 677dda9ab8a90e3c3092be99503327500a21a57a787ebcf285f5a9f227d53146
Tx public key: f61970c4f4fe17d906aa0b51a0ab38f592cbfb31e04d780dc79314896d4c8ca9
Timestamp: 1707731066 Timestamp [UCT]: 2024-02-12 09:44:26 Age [y:d:h:m:s]: 00:328:06:42:55
Block: 955831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235035 RingCT/type: yes/0
Extra: 01f61970c4f4fe17d906aa0b51a0ab38f592cbfb31e04d780dc79314896d4c8ca90211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66fb32df451e14b7499ac87f7f169fdc81a6ed33cebdc27c6ed7fc337510308e 0.600000000000 1415131 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": 955841, "vin": [ { "gen": { "height": 955831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66fb32df451e14b7499ac87f7f169fdc81a6ed33cebdc27c6ed7fc337510308e" } } ], "extra": [ 1, 246, 25, 112, 196, 244, 254, 23, 217, 6, 170, 11, 81, 160, 171, 56, 245, 146, 203, 251, 49, 224, 77, 120, 13, 199, 147, 20, 137, 109, 76, 140, 169, 2, 17, 0, 0, 0, 7, 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