Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 512bb4db28e52fce36616751cf9adcbe98b5105ffcaedfe1069afbbab8585bff

Tx prefix hash: 63dc8c6d410e11ba36b4f79d9fbb5b3199fe7be3832aaa0824a4c49d1a29e402
Tx public key: 0497e528f28f54471ef47ddaed945b3fc2272a394a33b80d5a0aab9e7e7b0b70
Timestamp: 1728906128 Timestamp [UCT]: 2024-10-14 11:42:08 Age [y:d:h:m:s]: 00:159:22:02:24
Block: 1131399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114062 RingCT/type: yes/0
Extra: 010497e528f28f54471ef47ddaed945b3fc2272a394a33b80d5a0aab9e7e7b0b70021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f13eb43e06f1e12dd4aa0f687b1c517a2e616b5761ec8534e9ba5cfc1475a85c 0.600000000000 1614298 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": 1131409, "vin": [ { "gen": { "height": 1131399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f13eb43e06f1e12dd4aa0f687b1c517a2e616b5761ec8534e9ba5cfc1475a85c" } } ], "extra": [ 1, 4, 151, 229, 40, 242, 143, 84, 71, 30, 244, 125, 218, 237, 148, 91, 63, 194, 39, 42, 57, 74, 51, 184, 13, 90, 10, 171, 158, 126, 123, 11, 112, 2, 17, 0, 0, 0, 8, 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