Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61387c6807f68750e1e70b53fe4a4823a43013dee5cdce9e3f6394fb24ac30ef

Tx prefix hash: e7bdd34c668e09b0b0b623637c87e41e9c52fbeefb71afc980c2d2f5c9414364
Tx public key: fc2479eb0e21a6b1d649c74f28ae48dd9ae4897c4691128d98999ebf59f089ac
Timestamp: 1726321866 Timestamp [UCT]: 2024-09-14 13:51:06 Age [y:d:h:m:s]: 00:074:21:39:08
Block: 1109967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53554 RingCT/type: yes/0
Extra: 01fc2479eb0e21a6b1d649c74f28ae48dd9ae4897c4691128d98999ebf59f089ac021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e79796e39222c251dc194fb90298d38e76ba052d1caca0cd7efb14d2b7779b09 0.600000000000 1588406 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": 1109977, "vin": [ { "gen": { "height": 1109967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e79796e39222c251dc194fb90298d38e76ba052d1caca0cd7efb14d2b7779b09" } } ], "extra": [ 1, 252, 36, 121, 235, 14, 33, 166, 177, 214, 73, 199, 79, 40, 174, 72, 221, 154, 228, 137, 124, 70, 145, 18, 141, 152, 153, 158, 191, 89, 240, 137, 172, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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