Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24a55e93114d493b9fd555947277803de067a96e93c4d23df0a4a835684fba09

Tx prefix hash: d0aaf6f917cd3c08c01b464ce01e6dc440abfccb91ee297b16507e3d0778423f
Tx public key: 0a441157a300ca166924057b65b04bbfcde4f43f78cb872e2ab34e3e8f993ca2
Timestamp: 1719081092 Timestamp [UCT]: 2024-06-22 18:31:32 Age [y:d:h:m:s]: 00:358:09:12:44
Block: 1049923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256059 RingCT/type: yes/0
Extra: 010a441157a300ca166924057b65b04bbfcde4f43f78cb872e2ab34e3e8f993ca2021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2f47fec88482d85d3be2515de6d3ff61881eb4c65e22ae19d23f14e53e1df6c 0.600000000000 1520038 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": 1049933, "vin": [ { "gen": { "height": 1049923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2f47fec88482d85d3be2515de6d3ff61881eb4c65e22ae19d23f14e53e1df6c" } } ], "extra": [ 1, 10, 68, 17, 87, 163, 0, 202, 22, 105, 36, 5, 123, 101, 176, 75, 191, 205, 228, 244, 63, 120, 203, 135, 46, 42, 179, 78, 62, 143, 153, 60, 162, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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