Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6e1435af969b64259c86c0bafeae154e1f73aa54a4ca37c061dec01fb18afc0

Tx prefix hash: 8d1ac0eadc89860433ceff5e28181068f54a6c5af65458fa8f377d090a8302d8
Tx public key: a4fde159c0b98c684f042e3b0fd0477b38a8eddec727111ab92e9a87a92fe806
Timestamp: 1737690470 Timestamp [UCT]: 2025-01-24 03:47:50 Age [y:d:h:m:s]: 00:144:12:24:56
Block: 1204017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103037 RingCT/type: yes/0
Extra: 01a4fde159c0b98c684f042e3b0fd0477b38a8eddec727111ab92e9a87a92fe8060211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83ad688d4e1a3de353f76ff3f1577ffe08ec8e56e2874f647beb41ab26eb0c53 0.600000000000 1690698 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": 1204027, "vin": [ { "gen": { "height": 1204017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83ad688d4e1a3de353f76ff3f1577ffe08ec8e56e2874f647beb41ab26eb0c53" } } ], "extra": [ 1, 164, 253, 225, 89, 192, 185, 140, 104, 79, 4, 46, 59, 15, 208, 71, 123, 56, 168, 237, 222, 199, 39, 17, 26, 185, 46, 154, 135, 169, 47, 232, 6, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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