Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c9674082d49ce99ca6e089ecf12ba1ea3b9246e62ee792f4d5bf2cbfda1823b

Tx prefix hash: 04ed290e5ff58c513c1c8a06f00f71cdea2d3d2f905feb521dd210383c11c3de
Tx public key: 5ca6e348c013b6abd1c01c2fdb192ae505a7011a6ce2795346c62add83848803
Timestamp: 1724026372 Timestamp [UCT]: 2024-08-19 00:12:52 Age [y:d:h:m:s]: 00:217:13:32:07
Block: 1090944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155349 RingCT/type: yes/0
Extra: 015ca6e348c013b6abd1c01c2fdb192ae505a7011a6ce2795346c62add8384880302110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e4000ff16e5c0c48dbe213c7d01b788e0d1772a9758ff275387abcaac22928c 0.600000000000 1565569 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": 1090954, "vin": [ { "gen": { "height": 1090944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e4000ff16e5c0c48dbe213c7d01b788e0d1772a9758ff275387abcaac22928c" } } ], "extra": [ 1, 92, 166, 227, 72, 192, 19, 182, 171, 209, 192, 28, 47, 219, 25, 42, 229, 5, 167, 1, 26, 108, 226, 121, 83, 70, 198, 42, 221, 131, 132, 136, 3, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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