Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34913b74df4946aada9184e35e8a7a2487962e861b25bdce3c7798b59dc243fe

Tx prefix hash: ec5ab29909e31c7c5f6fed8088550d56dbdbf046a3c95bf76969cbd6fff45364
Tx public key: 448edb6b0bcc13f1353d35be7c2e1436f5c8698162c989d13778a5c90a9e5319
Timestamp: 1708106871 Timestamp [UCT]: 2024-02-16 18:07:51 Age [y:d:h:m:s]: 00:281:16:18:42
Block: 958950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201673 RingCT/type: yes/0
Extra: 01448edb6b0bcc13f1353d35be7c2e1436f5c8698162c989d13778a5c90a9e531902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93b5b06eae36d32f553355dd6b80ff7787b28f9dab66a3012666a25be861c1a6 0.600000000000 1418421 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": 958960, "vin": [ { "gen": { "height": 958950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93b5b06eae36d32f553355dd6b80ff7787b28f9dab66a3012666a25be861c1a6" } } ], "extra": [ 1, 68, 142, 219, 107, 11, 204, 19, 241, 53, 61, 53, 190, 124, 46, 20, 54, 245, 200, 105, 129, 98, 201, 137, 209, 55, 120, 165, 201, 10, 158, 83, 25, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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